I think I'm asking the right question in the title but I will explain the situtaion just in case. This is a hypothetical situation so feel free to also respond with suggestions relative to a different approach. |
Re: Share licenses across multiple servers
You can point your client to a different database by creating a new DOORS icon shortcut, and adding the -d switch, in your case "-d 36677@server2". That shortcut's 'target' field might thus look like this:
If licensing works for the first database then it will work for the 2nd. This separation of licensing from data is real curious; it means companies cannot bill access to a database directly with licensing. There should be some mechanism for restricting which licensing is acceptable for a database. Not that I would ever ever ever ever actually do this, but I suppose maybe perhaps its possible for me to set up my license string to point to a sequencial list of known license serves around the company (semi-colon separated) to make sure that I do indeed get licensing whenever I need it.
|
Re: Share licenses across multiple servers llandale - Thu Oct 21 11:35:51 EDT 2010
You can point your client to a different database by creating a new DOORS icon shortcut, and adding the -d switch, in your case "-d 36677@server2". That shortcut's 'target' field might thus look like this:
If licensing works for the first database then it will work for the 2nd. This separation of licensing from data is real curious; it means companies cannot bill access to a database directly with licensing. There should be some mechanism for restricting which licensing is acceptable for a database. Not that I would ever ever ever ever actually do this, but I suppose maybe perhaps its possible for me to set up my license string to point to a sequencial list of known license serves around the company (semi-colon separated) to make sure that I do indeed get licensing whenever I need it.
Thanks for taking the time, Anthony |